Ensure that the length
property won't be *accidentally* accessed on a DecodeStream
-instance
#12365
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For these streams, compared to
Stream
andChunkedStream
, there's no well defined concept of length and consequently nolength
getter.[1] However, attempting to access the non-existentlength
won't currently error, but just returnundefined
, which could thus easily lead to bugs elsewhere in the code-base.[1] However, note that all stream implementations have an
isEmpty
getter which can be used instead.